README for the MASSES uv data for the pointing toward Per-emb-3.

Visibility (uv) data is delivered for both the spectral lines and continuum.

The format for each spectral line uv data file in a MASSES dataverse is:
[targetname].[configuration].[linename].[tracknumber].uvfits

The format for the continuum uv data in a MASSES dataverse is: 
[targetname].cont[wavelength].[sideband].[tracknumber].uvfits

Continuum uv data are delivered for 1.3 mm and 850 um.
The delivered spectral lines at 1.3 mm are 12CO21, 13CO21, C18O21, and N2DP.
The delivered spectral lines at 850 um are 12CO32, HCOP, H13COP.
This target also has imaged SWARM data at 1.3 mm and 850 um.
At 1.3 mm, the imaged lines are: c3h2, dcn32, dcop32, h2co303, h2co321, h2co322, sio54, so5544, and so5645.
At 850 um, the imaged lines are: 34so9887, cn5232, cn7252, cs76, dcn54, dcop54, h13cn43, hc15n43, hc18o43, hnc43, ocs2827, so7867, and so8877.
Table A3 in the full data release paper indicates which lines are detected for each pointing.

For Per-emb-3, there are two SUB tracks.
Track 151022 was taken with the ASIC correlator.
Track 180918 was taken with the SWARM correlator.
For Per-emb-3, there are two EXT tracks.
Track 161007 was taken with the SWARM correlator.
Track 161023 was taken with the SWARM correlator.
No 850 um data was taken in the EXT configuration.

To import uvfits files into miriad, the "fits" task should be used. "op=uvin" and "options=varwt" must be specified. We show an example for CO(2-1) below:
fits in=Per3.12CO21.151022.uvfits out=Per3.12CO21.151022.miriad.uv op=uvin options=varwt

To import into casa, the task importuvfits should be used:
importuvfits(fitsfile="Per3.12CO21.151022.uvfits",vis="Per3.12CO21.151022.casa.uv")
Rest frequencies for each spectral line need to be specified in casa to show proper velocities.

This dataset also includes the full SWARM visibility data.
If the user is only interested in continuum or the spectral lines 12CO21, 13CO21, C18O21, or N2DP, these datafiles do NOT need to be used. The user should only use the data specified above.
SWARM visibility data has NOT had the continuum subtracted, like the data discussed above.
The format for the SUB SWARM data is:
[targetname].SWARM.[wavelength].[chunk].[sideband].TRACK.uvfits
Four SWARM chunks are available for these SUB tracks.
The format for the EXT SWARM data is:
[targetname].SWARM.[wavelength].[chunk].[sideband].RECEIVERNUM.TRACK.uvfits
These EXT tracks had both SMA's 230 and 240 GHz receivers tuned to the same frequency. Both were combined when imaging.
Three SWARM chunks are available for each receiver of these EXT tracks.

These data can be imported in miriad or casa in the same way as above.
For these SWARM full visibility data, continuum subtraction should be done near the spectral line of interest.
Continuum subtraction can be done with miriad task 'uvlin' or with the casa task 'uvcontsub'.
